Task Files

Task files contain information that tells EDEN what you want to.  They are just small text files which can be created or modified by you as needed.  These files, along with your actual upload file, must be actively “sent” by you. Samples of what is contained in the task files are below with explanations.  The file names are in bold and not actually part of the file

SEND_CLAIMS TEST

                EDI08203

                MYED00

                M

                SENDCLAIM,TEST

This file tells EDEN who you are and that you are sending TEST claims! When EDEN sends back SEND       CLAIM you press command + R to send the claim file (Below named “eden.txt”).

SEND_CLAIMS PROD

                EDI08203

                MYED00

                M

                SENDCLAIM,PROD

This file tells EDEN who you are and that you are sending PRODuction claims! When EDEN sends back       SEND CLAIM you press command + R to send the claim file (Below named “eden.txt”).

GET_CONFIRM TASK

                                  EDI08203

                                  MYED00

                                  M

                                  RECCONF

This file tells EDEN who you are and that you want to RECeive a CONFirmation report.  This report tells           you if the file was accepted!  When EDEN sends back RECEIVE CONFIRMATION you press command + R to receive!

GET_VALID TASK

EDI08203

MYED00

M

RECVALID

This file tells EDEN who you are and that you want to RECeive a VALidation report.  This report tells       you which claims were accepted and so forth!  When EDEN sends back RECEIVE CONFIRMATION             you press command + R to receive!

Below is the actual screen output (annotated) from an upload to EDEN.  It shows what EDEN sent and how Zterm responded.  During your session it will be necessary for you to do certain things.  All in all, the EDEN system is not very friendly! This is going to change in the near future as EDEN moves to web-based file submissions and retrieval.

(Text in boldface is sent by Zterm)

CONNECT 9600 EDEN

                   WELCOME TO AT&T INFORMATION ACCESS SERVICE

Please Sign-on: edentst1

Password: gateway

Please Wait

2125719900/3123829114

FAC: p(128,128),w(2,2) COM

Renex Connect, SN-00400228

Enter service code - async

Connected to async host.

START

PROTOCOL

XMODEM1K

SEND TASK

C

(at this point you press command S and “send” the file “SEND_CLAIMS TASK)

### Send (X) SEND_CLAIMS TASK: 33 bytes, 0:10 elapsed, 3 cps, 0%

SEND CLAIM

C

(at this point you press command S and “send” your upload file, here “eden.txt”)

### Send (X) eden.txt: 36915 bytes, 1:54 elapsed, 321 cps, 33%

WORKING

CLAIM SENT SUCCESSFULLY

Session canceled due to async host disconnect.

Enter service code -

ATH (pressing command + h hangs up to phone)

OK

(At this point hand up.  Call back in two hours to get a confirmation report)

Zterm uses its own file to store the scripts used to go through the process above.  The file is named for the dialup name, here EDEN.  The “eden.zts” file is...

# Eden.zts - Logon script for Eden.  Starts after EDEN dialed

# wait for Eden prompt

wait prompt "Please Sign-on:"

send "edentst1^M"

wait prompt "Password:"

send "gateway^M"

wait prompt "Enter service code -"

send "async^M"

wait prompt "Connected to async host."

send "START^M"

wait prompt "PROTOCOL"

send "XMODEM1K^M"

If you follow the Zterm documentation you will understand what is happening so you can change things in the future.  Do not be scared to fool around.  That’s how you learn!  When you do your upload just follow the actual screen output on the previous page as your guide.

Make sure the files sent to you for Zterm are all in the same folder.  The ZPhoneList file has all the specific information by the receiving information, as shown below.  If you need to change this information follow the documentation that came with Zterm.

The Account and Password fields contain information used by Zterm’s automatic scripting system.  If you will be using a different software package, such as Microphone II or Microphone Pro, just use the same logon sequence as described above and in the supporting information printed by EDEN that you have received!